I love this book and i do not read very much. to be honest this is only the 3rd book i have read for just the sake of reading it. it was sitting at work someone had left it there and i picked it up. it is a bit slow in the very beginning and picks up in the 2 1/4 i love this book and i am going to get more from the author.

Grady's introduction excellently puts modernism in perspective in two ways. He shows its complexity, and then outlines some of its real continuities with postmodernism and pre-modern conceptions. He nevertheless finds good reasons for putting modernism in brackets so as to remind us that the first time modernism was challenged was 400 years ago when it began, before it became traditionalized. As a postmodernist with an acute sense of postmodernism's own limitations, he finds Shakespeare a valuable source for better understanding the postmodern critique of modernism.

This theoretical framework is presented with freshness, and it is essential to understanding his project. At the same time, his readings of his chosen plays do not require so much theoretical background. Grady's research shows that many of his points about characterizations, plots, and so on, are quite similar to points that have come before (and before this generation of critics).

Grady provides one of the stronger readings of Troilus and Cressida that I have seen, accounting for a large number of details and providing helpful glosses unmentioned in most other readings.

Grady's prose is heavy, but not too dense to be unreadable. Rather the book calls for an assiduous reading that will not feel tedious. Still one wonders whether, as in so much prose of its kind nowadays, more clarity might have been possible.

I found it readable and useful

Professor Grady's casebook is intended for law students, but the approach he takes is strikingly different from that of other casebooks. Professor Grady believes that appellate cases have two salient aspects: facts and holding. Thus, he edits the judges' opinions mercilessly, often reducing a multi-page case to a few lines. For the most part, doctrinal matters are not the focus of the book. Prof. Grady's approach is not to have students learn the application of "danger invites rescue" but to predict how a case will turn out. The theory is that the case law is, essentially axiomatically, consistent or discarded and that by knowing enough cases, one can predict the outcome of fact patterns. All of the important cases (_Palsgraf_, e.g.) are included, but Prof. Grady has a fondness for bizarre cases, and the book includes a large number of cases with bizarre fact patterns (the little boy who put newspaper down another boy's pants and set fire to the paper, e.g., or the circus horse that evacuated itself on a spectator). One obvious omission from the casebook is the area of defamation (including slander and libel). Overall, though, the casebook presents a wealth of cases, and the reader can predict case results with great accuracy. Topics covered include: strict liability, negligence, *res ipsa loquitur*, intentional torts, and negligent infliction of emotional distress.

Typical of most anthologies, some stories are clever, some entertaining, some funny, some boring, some touching... I can't really say which stories are best, since it really depends what style you like. Probably there is something for everyone but not everything for someone.

Most Civil War buffs concentrate upon the war east of the Mississippi. By comparison, the two battles of Pea Ridge and Prairie Grove are obscured by their distance from the main scene. I was interested, as my g-grandfather set up and ran a field hospital at Fayetteville, during the battle of Prairie Grove, Arkansas. The book is one of the best I've read in it's description of the tactics employed. Even better, the timely maps are simple, clear and placed closely to the verbage they cover. Similarly placed are short biographies of the major officers on each side of the battles. Unit narratives seldom drop below company level and the book cannot be considered an exhaustive study. But, at the end of 126 pages, a reader will have a sufficiently clear view of the events to gain a good grasp of the strategy and tactics used in these two important battles.

This book contains quite a lot of essential information about OOAD.

Too bad that the author makes no effort to explain it clearly. In fact I feel that the author made every effort to explain things in the hardest way possible. It might be a tactic to discourage the casual reader. It might be that the author thinks that making things easy to understand would degrade and spoil the fun of learning such difficult concepts.

Whatever the reason personally I think that if you have to write a book you should make it easy for your readers to understand what you want to say. Too bad because I think that the book is well rounded and contains a lot of useful data.

Buy it only if you have plenty of time to read the book carefully, over and over again.

Ignore the remarks about ego or over-rated, I found this book not easy to understand for a beginning student of Object Oriented Methodology, and I will have to re-read it. This is a very important book for all concerned, and is often quoted by Steve McConnell in his equally important "Code Complete" and "Rapid Development." Grady Booch refers quite often to real world object-oriented application models, to thinking along that line for solving real-world problems, and uses plenty of code examples from several different OOP languages including Smalltalk and C++. The goals of the book as outlined in the preface are to provide a sound understanding of the fundamental concepts of the object model, to facilitate the mastery of the notation and process of object-oriented analysis and design, and to teach the realistic application of object oriented development within a variety of problem domains. Last time I looked, this book is a listed selection for ICCP CCP certification, the mother of all certifications, and the choice of U.S. Armed Forces and Government Agencies. I personally prefer more interactive type of books that ease the student into the subject.

This book is not for 3rd grade students! It is for IT professionals already familiary with some form of development that can benefit from an OO development perspective. If people are looking for a 1+1 = 2 books, then go back to kindergarden.

I've read a few bashing remarks about this book being illegible and unnecessarily confusing. It is not. I read most of this book, and i must say it is a great reference on Object-Oriented design considerations.

He makes every attempt to give real world examples in his writing, something even a cat could probably make out.

After reading "Lobster Boy," the story of the murder of sideshow attraction Grady Stiles, I now understand why people can't turn away from a nasty auto accident: morbid fascination compels them to stare. The same is true for this book. I always felt a little strange and dirty after visiting a circus sideshow and that same feeling returned while reading this book. Rosen reveals a side to life that few people understand or have experienced. It's different and who's to say it's worse than what we know? Regardless, all the details are here for us to gawk at, like circus attraction. Although it suffers from weak writing, the story is gripping and you just can't turn away until it's over. Entertaining in a sleazy way.

Lobster Boy is a great story. Loads of conspiracy and action. The writing tends to become a bit dry in areas but if you can get through the minor writing flaws, it is a tremendously rewarding book.

In "Lobster Boy," Fred Rosen executes brilliantly the essential elements of a provocative story: strong character development, suspense, and attention to detail. The characters have distinct voices and successfully serve as foils and mirrors against each other. All of them reflect pieces of ourselves.

All in all, it was beautifully written; Rosen's crisp, poetic imagery and fluid language create a lush and present environment for a complex, deeply disturbing story. I was fascinated by how well Rosen navigated layers of psychological/family dynamics in this book. An incredibly realistic account, psychologically speaking, of the haunting emotional devastation wreaked upon a family given a father's narcissistic investment in his own fame --and a mother's passivity. Rosen's writing enables us to strengthen our awareness of political and sociological issues present in patriarchal culture, social class, and sideshows. This book had me turning one page after another, unable to set it down. When finished, I spent a long time discussing it over coffee; I was so moved by the book, as well as energized by Rosen's storytelling ability and insight. Highly recommended.

I do software development for many years and this book definitely is not what usually assumed by "user guide" title. UML is a language, and it should be treated as a language. Therefore I would compare the content of this book to extensive description of the language grammar, which is very dry and useless subject for practical person.

The book authors forgot that you cannot learn the language learning only its grammar - no way! Book does not show how language constructions actually work and what is the relative importance of different elements of the language when you try to describe your system.

Every chapter finishes with bunch of general advises how to apply UML to describe your system, but never shows how actually to do it for a specific system.

I read OMT book written by Rumbaugh and it was similar to this one. Both of them assumed that readers love UML/OMT for the sake of UML/OMT.

It is pity that such an exciting subject was converted into boring text by the authors who don't know how to write useful books.

A few months ago I've successfully completed an OO project. I used this book everyday for both analysis and design. It brought me new vision about some details and problems to dodge in my everyday's work. I confirm my first review: this book is really outstanding. UML concepts are explained thoroughly and clearly, even the most abstract concepts. PLUS, he gives you miscellaneous tips on how-to go more deeply in your analysis and design processing. Grady Booch gives you his experiences and feelings in OO technology; take it ... it's so valuable. All about UML is in this book. Buy it, read it and take whatever you want and apply it to your IT/OO problems ... you will be sucessful. Believe me Grady Booch is a great man/mentor as his colleagues Ivar Jacobson & James Rumbaugh, whose I used their notation and methodology before (OOSE & OMT). Amigos' books are references respecting UML. I am really surprise about bad reviews posted previously. Don't forget this book is just a User Guide; it won't fix any analysis or design for you. If you have appreciated Object-Oriented Analysis & Design with Applications and Object Solutions ... you will like this book.

This is the best book on UML. An excellent book on all aspects of UML methodology. This book comes from those who framed the methodology and that aspect makes it more valuable to the reader, experienced or otherwise.

The book starts of with reasons for modeling with real world examples. For a novice, this will be the best introduction to modeling - why is it needed in the first place.

The book also describes the evolution of UML (best practises of OOSE,OMT and Booch) which will benefit people in all levels of software engineering.

Any modeling technique needs to address the following three components a) Structural b) Behavioral and c) Architecture.

This book contains explanations for all of the above three components in separate sections. Even advance behavioral/structural modeling is discussed.

The structural modeling is described with explanations on a) Objects & classes b) relationship between classes c) class diagrams

The behavioral modeling is described with explanations on a) use case diagrams b) interaction diagrams c) activity diagrams and importantly d) state charts to name a few.

The architecture modeling is described with explanations on deployment, collaborations and component diagrams to name a few.

I would recommend interested OO developers/managers to acquire this book as a reference material for OO development needs.

I suppose that students at our school are representative for the worldwide population of cs students. This book is not at all an easy introduction to the unified process. Having been introduced to the principles of ooad in an earlier semester, and thus already knowing something about ooad, we were introduced to Jacobsons RUP. Their book contains a lot of knowledge, but unfortunately the authors are a) either not very good at explaining their knowledge b) hiding the knowledge to make it seem more intelligent than it really is or c) have written the book for people who already knows, at least something, about the unified process, or the objectory process that preceeded RUP. If you are looking for good illustrations and examples on how to model a system with uml and the added classifiers using the the RUP, then I suggest that you don't start with this book. You'll be disappointed. Working on our first project using the RUP, hearing complaints from nearly all students over the lack of understandable examples, I bought Jacobsons's earlier book - Object Oriented Software Engineering. In that book I found much better and concrete examples, which were very helpfull in understanding their latest book (but that shouldn't be necessary!). If you are looking for an easy introduction to the unified process, conveniently having things explained for you in an easy to understand way, then this is definitely not the book for you. Very poor examples - or should I say lack of good and understandable examples. On the other hand, if you don't know so much about ooad, has lots of time, likes to crack nuts, read between the lines and guess about this and that, then this book is for you. - I admit that after having gone through the hard process, gaining experience in RUP through a practical project, I have come to like the process and has found it very usefull. The principles of the RUP are sound and good. Now that I have gone through the struggle, and knows it better, I'm glad that I have it on my shelf. It contains a lot of usefull, but unfortunately poorly explained, and illustrated, information.

The arriving of UML has had a tremendous impact on the software world. With the speed of its acceptance UML has everyone talking in the same notation (if not the same language). This book takes the debate to the next logical level, which is the process of actually building complex software systems.

The Unified Process has the correct focus of building software for the users (requirements driven) in a given framework (architecture centric). It also emphasizes iterative development, which is a key success factor in today's market.

The book is well organized and extremely adept at tackling such a complex issue. By identifying artifacts, workers and workflow for every phase of software development, the book delivers actionable advice to project managers and software developers.

It is important to identify the book's focus and not confuse it with other topics, such as Business Process Reengineering and Object Reuse.

It is obvious that the Unified Process is a distillation of years of experience and should be a reference point for anyone who is trying to tackle software development

Most of us use a process to software development. Most of us do not use a formal process to do it. This book describes a formal process to software development. It is not the first book in its class nor is the last one. But it is one of the best I have ever read.

Ivar's describes the Unified Software Development Process from top to bottom (the workflows) and from minute 0 to project delivery (the phases) in great detail.

Be aware that this is not a object oriented analysis and design book. It is a software development process book.

He explains what is the role that every developer should have in every workflow (requirements, analysis, design, implementation) and also the list of deliverables in every phase.

The author explains in great detail what to look for (the goals) in every step on the software development. This is something that I have found really valuable.